Question regarding changes for mod_proxy on apache 1.3.X to 2.0X

This is a multi-part message in MIME format.

------=_NextPartTM-000-416eeae2-5338-45a9-81b2-3810831edc5a
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C2E7AE.34B640CD"

------_=_NextPart_001_01C2E7AE.34B640CD
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I hope this is the right mailing list to request information regarding =
the changes on mod_proxy from Apache 1.3 to apache 2.0
=20
We used in Apache 1.3.X the followin setup which no loner works under =
apacge 2.0 and I was wondering if any one can help. I have read the =
doc's regarding the new settings and directives however I still can not =
find and adequate solution.
=20
We use Virtual server with mod_proxy and have certain directories =
protected via password files.
The proxy is to a remote server and the password file is on the local =
apache proxy server.
=20
The configuration that works under 1.3 but no longer does on 2.0 is:
=20

UseCanonicalName off
ProxyRequests off=20
=20
ProxyPass / http://10.5.10.51
ProxyPassReverse / http://10.5.10.51


AllowOverride AuthConfig
AuthUserFile /etc/httpd/conf/passwd/adminpasswords
AuthName "Live Corp Admin"
AuthType Basic
require valid-user admin


ServerName yyy.yyy.com
ServerAlias yyy
ServerAdmin admin@localhost
ErrorLog /var/log/httpd/error_log_Virtual_yyy
TransferLog /var/log/httpd/access_log_virtual_yyy
=20
=20

------_=_NextPart_001_01C2E7AE.34B640CD
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



charset=3Diso-8859-1">

Re: Question regarding changes for mod_proxy on apache 1.3.X to2.0X

Jorge Reyes wrote:

> I hope this is the right mailing list to request information regarding
> the changes on mod_proxy from Apache 1.3 to apache 2.0

A better place to post this would be the main dev@httpd.apache.org
mailing list, as your question has to do with authentication.

> The configuration that works under 1.3 but no longer does on 2.0 is:

Define "no longer works".

Regards,
Graham
--
-----------------------------------------
minfrin@sharp.fm "There's a moon
over Bourbon Street
tonight..."

RE: Question regarding changes for mod_proxy on apache 1.3.X to 2.0X

Thanks I will try to post on that mailing list.
PS

"No Longer Works" means:
On Apache 1.3.x the user who type http://www.zyx.com/admin would be =
presented with an authetication window, on apache 2.0 the request fails =
and the log file (error log) reads:
=20
[Tue Mar 11 00:06:18 2003] [error] [client 111.111.111.111] proxy: DNS =
lookup failure for: 10.5.10.51error returned by =
/error/HTTP_UNAUTHORIZED.html.var

I have read the doc's regarding the new settings and directives however =
I still can not find and adequate solution.

-----Original Message-----
From: Graham Leggett [mailto:minfrin@sharp.fm]
Sent: Tuesday, March 11, 2003 1:56 AM
To: modproxy-dev@apache.org
Subject: Re: Question regarding changes for mod_proxy on apache 1.3.X to
2.0X


Jorge Reyes wrote:

> I hope this is the right mailing list to request information regarding =

> the changes on mod_proxy from Apache 1.3 to apache 2.0

A better place to post this would be the main dev@httpd.apache.org=20
mailing list, as your question has to do with authentication.

> The configuration that works under 1.3 but no longer does on 2.0 is:

Define "no longer works".

Regards,
Graham
--=20
-----------------------------------------
minfrin@sharp.fm "There's a moon
over Bourbon Street
tonight..."

Re: Question regarding changes for mod_proxy on apache 1.3.X to2.0X

sounds like a bug to me.

a quick workaround:
maybe you change the proxypass to use a hostname instead of an IP #.
It could also be that you haven't got your reverse IP set up for that
machine. and it can't create the x-forwarded-for line.

cheers
ian

you should probably raise a bugzilla via nagoya.apache.org


Jorge Reyes wrote:
> Thanks I will try to post on that mailing list.
> PS
>
> "No Longer Works" means:
> On Apache 1.3.x the user who type http://www.zyx.com/admin would be presented with an authetication window, on apache 2.0 the request fails and the log file (error log) reads:
>
> [Tue Mar 11 00:06:18 2003] [error] [client 111.111.111.111] proxy: DNS lookup failure for: 10.5.10.51error returned by /error/HTTP_UNAUTHORIZED.html.var
>
> I have read the doc's regarding the new settings and directives however I still can not find and adequate solution.
>
> -----Original Message-----
> From: Graham Leggett [mailto:minfrin@sharp.fm]
> Sent: Tuesday, March 11, 2003 1:56 AM
> To: modproxy-dev@apache.org
> Subject: Re: Question regarding changes for mod_proxy on apache 1.3.X to
> 2.0X
>
>
> Jorge Reyes wrote:
>
>
>>I hope this is the right mailing list to request information regarding
>>the changes on mod_proxy from Apache 1.3 to apache 2.0
>
>
> A better place to post this would be the main dev@httpd.apache.org
> mailing list, as your question has to do with authentication.
>
>
>>The configuration that works under 1.3 but no longer does on 2.0 is:
>
>
> Define "no longer works".
>
> Regards,
> Graham